how-zkagi-os-works
How does ZkAGI OS work?
At its core, ZkAGI represents a cluster of compute devices (CPUs, GPUs, TEEs with GPUs) forming a DePIN network on which AI models are hosted and agents leverage these models for on-chain and off-chain actions. ZkAGI is a network of public and private subnets comprising nodes running ZkAGI OS -- these nodes can be desktops, VPS instances, or Telegram app instances.
- Each node has a wallet attached (base chain is Solana, with omni-chain perspective and Base integrations coming)
- Each node runs an agent or pack of agents configured for social automation, trading, media creation, and productivity tasks
- Multiple agents can run simultaneously from the same node instance
How are wallet keys managed for ZkAGI agents?
ZkAGI supports multiple wallet key storage strategies depending on the level of autonomy and security required. Keys can be stored locally, in TEEs for autonomous custody, or in secure hashed databases with 2FA for human-authenticated execution.
- Local storage -- keys stored on user's machine or VPS; automations work with self-custodial wallets locally
- TEE storage -- agent/autonomous custody and signing inside Trusted Execution Environments
- Secure hashed databases with dynamic salt -- agent recommends actions, but user must authenticate with both a password and 2FA before execution
How do nodes earn rewards in the ZkAGI network?
Nodes with idle CPU or GPU capacity (typically desktops) can earn native tokens by committing their idle power into the ZkAGI compute cluster. Currently the network rewards XPs, which will convert to tokens once the token goes live according to a fair distribution plan.
- Idle CPU/GPU can be committed to the ZkAGI compute cluster for rewards
- Currently earning XPs (no token yet -- will be announced ahead of time)
- XPs will convert to a defined number of tokens upon token launch, with details shared with the community
What is the difference between public and private subnets?
The ZkAGI network runs two types of subnets in parallel: one public subnet containing shared AI models (the community/super agent network) and multiple private subnets each containing a private swarm of secret agents. The key difference is the level of user and on-chain privacy granted to agents and human users.
-
Public subnet (one):
- Accessible through ZkTerminal and the Zynapse API out of the box
- Shared AI models for the community / super agent network
- zk-verification available
-
Private subnets (multiple possible):
- Developers assemble their own cluster with mechanics similar to the ZkAGI network
- Uses a new model copy of open-source models
- Storage across TEE nodes for data and compute privacy
- zk-verification available
- PETs (Privacy Enhancing Technologies) assembled for training and fine-tuning to ensure data privacy
- Techniques include Hybrid FHE, federated training, and MPCs for privacy during training
-
For private subnet assembly, contact [email protected]